-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Drop usage of v1beta1 conditions #12109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 Drop usage of v1beta1 conditions #12109
Conversation
/test? |
@fabriziopandini: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
2 similar comments
/test pull-cluster-api-e2e-conformance-ci-latest-main |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
8816570
to
5e3fd7f
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main |
5e3fd7f
to
754995b
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main |
…conditions management only)
# Conflicts: # internal/controllers/machine/machine_controller_test.go
…trolplanev1.ControlPlaneComponentsHealthyV1Beta1Condition in controllers
754995b
to
e06c3bc
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main |
/test pull-cluster-api-e2e-latestk8s-main Looks like just a flake |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
e75694c
to
3e469fe
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main |
@fabriziopandini: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Thx! Very nice work! /lgtm |
LGTM label has been added. Git tree hash: b721225c9cdd0328b0aa8c7ce06956cdc5310a37
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Accept usage of clusterv1.ResizedV1Beta1Condition (it is for v1beta1 conditions management only) * Stop using clusterv1.ClusterClassVariablesReconciledV1Beta1Condition in controllers * Stop using clusterv1.TopologyReconciledV1Beta1Condition in controllers * Stop using clusterv1.MachineNodeHealthyV1Beta1Condition in controllers # Conflicts: # internal/controllers/machine/machine_controller_test.go * Stop using clusterv1.PreTerminateDeleteHookSucceededV1Beta1Condition in controllers * Stop using clusterv1.DrainingSucceededV1Beta1Condition in controllers * Stop using clusterv1.VolumeDetachSucceededV1Beta1Condition in controllers * Stop using clusterv1.BootstrapReadyV1Beta1Condition in controllers * Stop using clusterv1.ControlPlaneInitializedV1Beta1Condition in controllers * Stop using clusterv1.InfrastructureReadyV1Beta1Condition in controllers * Stop using clusterv1.ReadyV1Beta1Condition in controllers * Stop using clusterv1.MachineOwnerRemediatedV1Beta1Condition and clusterv1.MachineHealthCheckSucceededV1Beta1Condition in controllers * Stop using clusterv1.bootstrapv1.DataSecretAvailableV1Beta1Condition in controllers * Stop using controlplanev1.KubeadmControlPlaneMachine*HealthyCondition in controllers * Stop using controlplanev1.controlplanev1.AvailableV1Beta1Condition in controllers * Stop using controlplanev1..EtcdClusterHealthyV1Beta1Condition and controlplanev1.ControlPlaneComponentsHealthyV1Beta1Condition in controllers * Drop unnecessary TODO * Small cleanups * Fix tests * Address comments * More comments
What this PR does / why we need it:
Do not review, work in progress, I'm using this PR mostly to check everything looks good in CI but most probably I will later re-submit in a few smaller PR
Which issue(s) this PR fixes:
Fixes #
/area conditions